Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3044b5bdc4bedb327bbf6fd54b3fa658fe3367dedae264a9bb20ab579af26161

Tx prefix hash: bafb005f911dbd39a2b1a4e9a74b5317de30c25a45ebe937e422ae950a8f5b85
Tx public key: 73cb7680191ef0a0c6b54f35561b2a519ef4d581e2646a8320107df39a7d4ef1
Timestamp: 1726513193 Timestamp [UCT]: 2024-09-16 18:59:53 Age [y:d:h:m:s]: 00:159:19:54:44
Block: 1111549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114014 RingCT/type: yes/0
Extra: 0173cb7680191ef0a0c6b54f35561b2a519ef4d581e2646a8320107df39a7d4ef1021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 046ca84caffa171ced9faa06f3bd8add2703f2c5fcaca457b9ec40b20d2be392 0.600000000000 1590550 of 15

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": 1111559, "vin": [ { "gen": { "height": 1111549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "046ca84caffa171ced9faa06f3bd8add2703f2c5fcaca457b9ec40b20d2be392" } } ], "extra": [ 1, 115, 203, 118, 128, 25, 30, 240, 160, 198, 181, 79, 53, 86, 27, 42, 81, 158, 244, 213, 129, 226, 100, 106, 131, 32, 16, 125, 243, 154, 125, 78, 241, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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