Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 956f37040c32c66983f1b183e4294f1f3e97bee2ac669e16d54b31478a948b4b

Tx prefix hash: 498f5dae95009a5e7d48cbbc25e42609f6876a047c92cc7b1d021304c03b0456
Tx public key: 8aeea951e0c987e8f984a41e033f891b4311d3cb057a632bf3f9757d9c8f1c14
Timestamp: 1733710076 Timestamp [UCT]: 2024-12-09 02:07:56 Age [y:d:h:m:s]: 00:122:04:44:11
Block: 1171126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87125 RingCT/type: yes/0
Extra: 018aeea951e0c987e8f984a41e033f891b4311d3cb057a632bf3f9757d9c8f1c1402110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eaa19244c7e5e6dd91581a0ae05fcde19833e3fe888f9b5707c5ffcc15fec8c 0.600000000000 1656863 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": 1171136, "vin": [ { "gen": { "height": 1171126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eaa19244c7e5e6dd91581a0ae05fcde19833e3fe888f9b5707c5ffcc15fec8c" } } ], "extra": [ 1, 138, 238, 169, 81, 224, 201, 135, 232, 249, 132, 164, 30, 3, 63, 137, 27, 67, 17, 211, 203, 5, 122, 99, 43, 243, 249, 117, 125, 156, 143, 28, 20, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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