Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49c0919601d65c930de681fd4e3190266d6266329367e57af9adbe151fba23dd

Tx prefix hash: 22e53fef43a194f9558d6149f76853ec9588dd4745f7a44c5f655fd4ef188a89
Tx public key: fee104413b9cdb4c75eb8136cd17df4e0fda3d09679e94c60108d3e7c3f6a33e
Timestamp: 1755091750 Timestamp [UCT]: 2025-08-13 13:29:10 Age [y:d:h:m:s]: 00:100:01:34:16
Block: 1346094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70926 RingCT/type: yes/0
Extra: 01fee104413b9cdb4c75eb8136cd17df4e0fda3d09679e94c60108d3e7c3f6a33e021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 054036b0e8a959ce30382c21b2e9484c116fbc1358bdcf6886a5eedd92fa3292 0.600000000000 1833991 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": 1346104, "vin": [ { "gen": { "height": 1346094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "054036b0e8a959ce30382c21b2e9484c116fbc1358bdcf6886a5eedd92fa3292" } } ], "extra": [ 1, 254, 225, 4, 65, 59, 156, 219, 76, 117, 235, 129, 54, 205, 23, 223, 78, 15, 218, 61, 9, 103, 158, 148, 198, 1, 8, 211, 231, 195, 246, 163, 62, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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