Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bcdb7dbdc9704944e3eea5f9d9e0f647ae98caa740e7ced1fb31afa3f8d07e9

Tx prefix hash: e108292304c5cad29e07e2637ec8012f10ab87fb377f47b5d9e106f86b85ab2d
Tx public key: 5955dce16f04df580ebd9105c19f2b8aead9a2f4d47ed7af96e8e3ed9172be8e
Timestamp: 1753722012 Timestamp [UCT]: 2025-07-28 17:00:12 Age [y:d:h:m:s]: 00:151:21:51:53
Block: 1335339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107463 RingCT/type: yes/0
Extra: 015955dce16f04df580ebd9105c19f2b8aead9a2f4d47ed7af96e8e3ed9172be8e021100000001db6acbd3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d7fb94e6dbcf1a0a286c88a8333534038d05c175511acb4eacb1beac3a0d73a 0.600000000000 1823140 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": 1335349, "vin": [ { "gen": { "height": 1335339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d7fb94e6dbcf1a0a286c88a8333534038d05c175511acb4eacb1beac3a0d73a" } } ], "extra": [ 1, 89, 85, 220, 225, 111, 4, 223, 88, 14, 189, 145, 5, 193, 159, 43, 138, 234, 217, 162, 244, 212, 126, 215, 175, 150, 232, 227, 237, 145, 114, 190, 142, 2, 17, 0, 0, 0, 1, 219, 106, 203, 211, 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