Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7494e407f646e33e460a9ad912b8ad6df3e6cd58aef61a4db60816fb0be88c61

Tx prefix hash: e97b200a06b78fb08ed1b2db0875b0afe92a99663070a2f0d91f1b3705e6cf60
Tx public key: 95a47b0dc82d806cd8317bee1130d7e5f932e8af5ce7bf0baa5ba6b0d5d3903a
Timestamp: 1697179977 Timestamp [UCT]: 2023-10-13 06:52:57 Age [y:d:h:m:s]: 01:158:07:16:13
Block: 868570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374184 RingCT/type: yes/0
Extra: 0195a47b0dc82d806cd8317bee1130d7e5f932e8af5ce7bf0baa5ba6b0d5d3903a021100000001faf35c9c000000000000000000

1 output(s) for total of 0.812956034000 dcy

stealth address amount amount idx
00: 3cfa0539f84686c2ce2710d9cf91ca29f587270af62ab735af150481aed818d4 0.812956034000 1323387 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": 868580, "vin": [ { "gen": { "height": 868570 } } ], "vout": [ { "amount": 812956034, "target": { "key": "3cfa0539f84686c2ce2710d9cf91ca29f587270af62ab735af150481aed818d4" } } ], "extra": [ 1, 149, 164, 123, 13, 200, 45, 128, 108, 216, 49, 123, 238, 17, 48, 215, 229, 249, 50, 232, 175, 92, 231, 191, 11, 170, 91, 166, 176, 213, 211, 144, 58, 2, 17, 0, 0, 0, 1, 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