Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 188db4813a6d4fdbb4f8c4de542fcf8982e78966da45bf93109f77baedd5643d

Tx prefix hash: 36fa83b3b7a8e1a94d103fe7cb4f9cb5854e4126ea5e32709a3973a6a9a4f633
Tx public key: a5510d1a6c14a74da2a0b3e5bbccaa7d68f8da9c968a24511e3eb38dd8e98ed9
Timestamp: 1695549218 Timestamp [UCT]: 2023-09-24 09:53:38 Age [y:d:h:m:s]: 01:194:05:22:11
Block: 855045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399874 RingCT/type: yes/0
Extra: 01a5510d1a6c14a74da2a0b3e5bbccaa7d68f8da9c968a24511e3eb38dd8e98ed902110000000833af99f4000000000000000000

1 output(s) for total of 0.901324172000 dcy

stealth address amount amount idx
00: 8067c768b06750ae65a863e542917d9b8caa528278fc901fc5fa6fd3947d4853 0.901324172000 1309047 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": 855055, "vin": [ { "gen": { "height": 855045 } } ], "vout": [ { "amount": 901324172, "target": { "key": "8067c768b06750ae65a863e542917d9b8caa528278fc901fc5fa6fd3947d4853" } } ], "extra": [ 1, 165, 81, 13, 26, 108, 20, 167, 77, 162, 160, 179, 229, 187, 204, 170, 125, 104, 248, 218, 156, 150, 138, 36, 81, 30, 62, 179, 141, 216, 233, 142, 217, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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