Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 19847b4c619755e3bd3965663021686d6669473de7428d1ffe0a159d4e842f4d

Tx prefix hash: 604b4f9140ca18d61010824cdef519c08be9a3204dd619921659c74190ada573
Tx public key: f062ab7fb9cf243fb01bd4ee75cc6515cf94e376b94163d1eea0f976c3055b11
Timestamp: 1698508987 Timestamp [UCT]: 2023-10-28 16:03:07 Age [y:d:h:m:s]: 02:039:09:55:51
Block: 879598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547777 RingCT/type: yes/0
Extra: 01f062ab7fb9cf243fb01bd4ee75cc6515cf94e376b94163d1eea0f976c3055b11021100000004faf35c9c000000000000000000

1 output(s) for total of 0.747354581000 dcy

stealth address amount amount idx
00: dc7509558b2cc1efc828d69dbd9a05e1ef6285b020bbdd19f3d86372d4aceb5b 0.747354581000 1335132 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 879608, "vin": [ { "gen": { "height": 879598 } } ], "vout": [ { "amount": 747354581, "target": { "key": "dc7509558b2cc1efc828d69dbd9a05e1ef6285b020bbdd19f3d86372d4aceb5b" } } ], "extra": [ 1, 240, 98, 171, 127, 185, 207, 36, 63, 176, 27, 212, 238, 117, 204, 101, 21, 207, 148, 227, 118, 185, 65, 99, 209, 238, 160, 249, 118, 195, 5, 91, 17, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8