Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18352080828a41ce2d6d939c40bec4b06bf8556f426da9a39ac07150ed01c041

Tx prefix hash: 230f85add2e7c83f916ad4d7b0e36988c603fb3467c684f363b217f8140c2df0
Tx public key: 44a753dcc0df0e7aa4a1086b513b62986b638c6cf77caf8b851885b1a5692389
Timestamp: 1717744551 Timestamp [UCT]: 2024-06-07 07:15:51 Age [y:d:h:m:s]: 01:153:21:41:50
Block: 1038864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368561 RingCT/type: yes/0
Extra: 0144a753dcc0df0e7aa4a1086b513b62986b638c6cf77caf8b851885b1a5692389021100000006d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9992173954b6041365cdc3226133d849385f8d76aef5adb8dfd22dd8fb0434b1 0.600000000000 1507425 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": 1038874, "vin": [ { "gen": { "height": 1038864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9992173954b6041365cdc3226133d849385f8d76aef5adb8dfd22dd8fb0434b1" } } ], "extra": [ 1, 68, 167, 83, 220, 192, 223, 14, 122, 164, 161, 8, 107, 81, 59, 98, 152, 107, 99, 140, 108, 247, 124, 175, 139, 133, 24, 133, 177, 165, 105, 35, 137, 2, 17, 0, 0, 0, 6, 215, 73, 245, 17, 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