Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef15167a90d1f44aaa0cc4cbd8288165e3e3fbbc217ca595ffa557e600f2acdc

Tx prefix hash: 283b523e1a5525fcde34f954328421a1a5e42216904c123b679bc5ac418b5056
Tx public key: 9de915b35c316c67383fe7d26929f803d02629033ae624b1bb4e1def6a131947
Timestamp: 1716302264 Timestamp [UCT]: 2024-05-21 14:37:44 Age [y:d:h:m:s]: 00:187:08:38:46
Block: 1026910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134098 RingCT/type: yes/0
Extra: 019de915b35c316c67383fe7d26929f803d02629033ae624b1bb4e1def6a13194702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8eb9ce67b18054599dfaf93c0e230cb8870060de1b944d19c6e8d8290ffcb920 0.600000000000 1494249 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": 1026920, "vin": [ { "gen": { "height": 1026910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8eb9ce67b18054599dfaf93c0e230cb8870060de1b944d19c6e8d8290ffcb920" } } ], "extra": [ 1, 157, 233, 21, 179, 92, 49, 108, 103, 56, 63, 231, 210, 105, 41, 248, 3, 208, 38, 41, 3, 58, 230, 36, 177, 187, 78, 29, 239, 106, 19, 25, 71, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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