Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19d5bd01ac595d30037b426e23123db81166759c74eae4c9d3d4c3b1dca0708e

Tx prefix hash: 7e5555f40ff9468b8f88d0b5a904cb74f00473dd56d744ce922f7089bf6b4ca7
Tx public key: c2b7d03197f2d0b7d9aac39851c9bee3420cd8c9109651247a941bfdcc3167fd
Timestamp: 1587782374 Timestamp [UCT]: 2020-04-25 02:39:34 Age [y:d:h:m:s]: 04:265:23:31:52
Block: 95575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1101995 RingCT/type: yes/0
Extra: 01c2b7d03197f2d0b7d9aac39851c9bee3420cd8c9109651247a941bfdcc3167fd0211000000d660e3cc90000000000000000000

1 output(s) for total of 296.020042949000 dcy

stealth address amount amount idx
00: 1184d910bc5ae0282dfdef9400fbb3a60809d63c9fa1d71a2268a09089eef4dd 296.020042949000 169824 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": 95585, "vin": [ { "gen": { "height": 95575 } } ], "vout": [ { "amount": 296020042949, "target": { "key": "1184d910bc5ae0282dfdef9400fbb3a60809d63c9fa1d71a2268a09089eef4dd" } } ], "extra": [ 1, 194, 183, 208, 49, 151, 242, 208, 183, 217, 170, 195, 152, 81, 201, 190, 227, 66, 12, 216, 201, 16, 150, 81, 36, 122, 148, 27, 253, 204, 49, 103, 253, 2, 17, 0, 0, 0, 214, 96, 227, 204, 144, 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