Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 498b90c1fa8a2cbb0478b58a02ba093c17fc0e90db3656ed204943783fc3e247

Tx prefix hash: e2e470a0d59dfc31b349dad1ef54e783f6ca2d369145dbc0ede745db4dd7e99b
Tx public key: 565ab6b27f1b6cd9ecc8ad6c6f40a39a2142e7688dd67df3caa03a9447e9b83b
Timestamp: 1711974017 Timestamp [UCT]: 2024-04-01 12:20:17 Age [y:d:h:m:s]: 01:226:21:14:07
Block: 990988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420873 RingCT/type: yes/0
Extra: 01565ab6b27f1b6cd9ecc8ad6c6f40a39a2142e7688dd67df3caa03a9447e9b83b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b22e98acec87371a77407ce6da305e72c39ee75237bebaa0bb458b46dc77770a 0.600000000000 1451320 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": 990998, "vin": [ { "gen": { "height": 990988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b22e98acec87371a77407ce6da305e72c39ee75237bebaa0bb458b46dc77770a" } } ], "extra": [ 1, 86, 90, 182, 178, 127, 27, 108, 217, 236, 200, 173, 108, 111, 64, 163, 154, 33, 66, 231, 104, 141, 214, 125, 243, 202, 160, 58, 148, 71, 233, 184, 59, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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