Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f74c47cea0f3f0b50a4f2b5cd70da82e602e9f300e347854eb78f495a2dc770

Tx prefix hash: bc5ccca5d174de6b8318867728746ecc95e9783e5218e1dd5df896df722bf56d
Tx public key: e678de2dd415a1e3e09865d4e3abeaddb8b22759d6b06e65ecc402d32969ce3e
Timestamp: 1747669595 Timestamp [UCT]: 2025-05-19 15:46:35 Age [y:d:h:m:s]: 00:184:20:17:11
Block: 1286414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129805 RingCT/type: yes/0
Extra: 01e678de2dd415a1e3e09865d4e3abeaddb8b22759d6b06e65ecc402d32969ce3e0211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 848f7d1af94c2649141d507ca1048b5e85cbae16260cb317d16dbdfc96cd48f1 0.600000000000 1773879 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": 1286424, "vin": [ { "gen": { "height": 1286414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "848f7d1af94c2649141d507ca1048b5e85cbae16260cb317d16dbdfc96cd48f1" } } ], "extra": [ 1, 230, 120, 222, 45, 212, 21, 161, 227, 224, 152, 101, 212, 227, 171, 234, 221, 184, 178, 39, 89, 214, 176, 110, 101, 236, 196, 2, 211, 41, 105, 206, 62, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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