Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1794a3083cf74e5b06ceafea476631a13245586705f00d10c7ed38dcec2ab42d

Tx prefix hash: 7f5341a4a11328d9d0e684a93c3319956f17ae53c80489b76b18f1c71b513151
Tx public key: 8019df03f8049f9d796fa9b00f265d04f3a3eab3b6c0bc01991d73b06477b244
Timestamp: 1748855074 Timestamp [UCT]: 2025-06-02 09:04:34 Age [y:d:h:m:s]: 00:171:23:42:53
Block: 1296241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120587 RingCT/type: yes/0
Extra: 018019df03f8049f9d796fa9b00f265d04f3a3eab3b6c0bc01991d73b06477b24402110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5207a6eb45a0bd8daf8a6c630574eed6e02141f0bb13e0a300cc92f035f7379 0.600000000000 1783748 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": 1296251, "vin": [ { "gen": { "height": 1296241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5207a6eb45a0bd8daf8a6c630574eed6e02141f0bb13e0a300cc92f035f7379" } } ], "extra": [ 1, 128, 25, 223, 3, 248, 4, 159, 157, 121, 111, 169, 176, 15, 38, 93, 4, 243, 163, 234, 179, 182, 192, 188, 1, 153, 29, 115, 176, 100, 119, 178, 68, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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