Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec8ad96bca5f16ab03ca955fb689d51fbec89905e2c9f8ecf1b8c5e7f9c182fd

Tx prefix hash: b878d42a918a50da2b8ff0f1dca9527b8416c3e1fdd844696bfd7b590e421f5f
Tx public key: 8fe093b979bf3e9d471e3fba71dd8c09b2157c6dd6f45944c6dced7505eafb88
Timestamp: 1764070315 Timestamp [UCT]: 2025-11-25 11:31:55 Age [y:d:h:m:s]: 00:002:11:02:45
Block: 1419794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1771 RingCT/type: yes/0
Extra: 018fe093b979bf3e9d471e3fba71dd8c09b2157c6dd6f45944c6dced7505eafb8802110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fefbcd03a0f5152e5063382054213ef174f3ac406a936a3505de14539325d60 0.600000000000 1908335 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": 1419804, "vin": [ { "gen": { "height": 1419794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fefbcd03a0f5152e5063382054213ef174f3ac406a936a3505de14539325d60" } } ], "extra": [ 1, 143, 224, 147, 185, 121, 191, 62, 157, 71, 30, 63, 186, 113, 221, 140, 9, 178, 21, 124, 109, 214, 244, 89, 68, 198, 220, 237, 117, 5, 234, 251, 136, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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