Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae96f51007b57e13fb0d57f7f8e3d5f9a5314680867a44f834b5ad6144a5bbe7

Tx prefix hash: 49470fe4299a29d9bf1c1f2ac3d50f719b766472f72f0274435f29e023dd0ae0
Tx public key: b39486fc2859dc5214464e3d6171b6c6b162f90fa11e8812f1657c8db4cea12e
Timestamp: 1727156455 Timestamp [UCT]: 2024-09-24 05:40:55 Age [y:d:h:m:s]: 01:015:01:57:28
Block: 1116888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269124 RingCT/type: yes/0
Extra: 01b39486fc2859dc5214464e3d6171b6c6b162f90fa11e8812f1657c8db4cea12e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c048fdd18e9de175b91689da9d30984649194b0105e53b5771f46a2fe39e62b7 0.600000000000 1597527 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": 1116898, "vin": [ { "gen": { "height": 1116888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c048fdd18e9de175b91689da9d30984649194b0105e53b5771f46a2fe39e62b7" } } ], "extra": [ 1, 179, 148, 134, 252, 40, 89, 220, 82, 20, 70, 78, 61, 97, 113, 182, 198, 177, 98, 249, 15, 161, 30, 136, 18, 241, 101, 124, 141, 180, 206, 161, 46, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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