Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15c37e18e61667572f8d7e54ea6de419c7c9f6aad2ed9dc290899c3c46357ddc

Tx prefix hash: 9aa1042babc12c70ffda3e3a50c85bb0c893fe9d4b71e9ea3b464d9fc7d47ac2
Tx public key: ff6d3ac3fb69bea2fd2847e2eb79a7ff1eb96316c0c573235ecd730c5e675f8a
Timestamp: 1741787611 Timestamp [UCT]: 2025-03-12 13:53:31 Age [y:d:h:m:s]: 00:324:15:16:51
Block: 1237734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229656 RingCT/type: yes/0
Extra: 01ff6d3ac3fb69bea2fd2847e2eb79a7ff1eb96316c0c573235ecd730c5e675f8a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b074a936c689cf2d7953a6aa09002428cd32643e8147f5214fd38722e5bdff6e 0.600000000000 1724691 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": 1237744, "vin": [ { "gen": { "height": 1237734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b074a936c689cf2d7953a6aa09002428cd32643e8147f5214fd38722e5bdff6e" } } ], "extra": [ 1, 255, 109, 58, 195, 251, 105, 190, 162, 253, 40, 71, 226, 235, 121, 167, 255, 30, 185, 99, 22, 192, 197, 115, 35, 94, 205, 115, 12, 94, 103, 95, 138, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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