Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eeda5b203b3e6ee5b09a146d297ada71c4aaeeb9cf02826f6b3079da5c3c7270

Tx prefix hash: 76c0ec67df70bc0015e080bc199ba69b7e8833b4e4e603d9db11dc21ddbe9ed5
Tx public key: 9238967b4900bbf5f88fd4b2bcd452447616a6592a22c6462ba52f13f33fdcdd
Timestamp: 1714469467 Timestamp [UCT]: 2024-04-30 09:31:07 Age [y:d:h:m:s]: 00:303:06:48:20
Block: 1011708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216772 RingCT/type: yes/0
Extra: 019238967b4900bbf5f88fd4b2bcd452447616a6592a22c6462ba52f13f33fdcdd02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 483d70ec90ac3603d16d25f22b64f0b2e515a5570e635013fe675cfd3a37bce8 0.600000000000 1474006 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": 1011718, "vin": [ { "gen": { "height": 1011708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "483d70ec90ac3603d16d25f22b64f0b2e515a5570e635013fe675cfd3a37bce8" } } ], "extra": [ 1, 146, 56, 150, 123, 73, 0, 187, 245, 248, 143, 212, 178, 188, 212, 82, 68, 118, 22, 166, 89, 42, 34, 198, 70, 43, 165, 47, 19, 243, 63, 220, 221, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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