Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22bca7d0f9f9a012508b8133039ff7022d8ec5fe5350fa42531ba0e96f68c367

Tx prefix hash: e4ccf0203f61dcb755025f37f91bcf2359840934545bf16c855c542b4c2fbd88
Tx public key: 05a7d389cafd7da0998990ce123e3d8b84b8c6d9e71695339a9c28aa0153d7e7
Timestamp: 1727266228 Timestamp [UCT]: 2024-09-25 12:10:28 Age [y:d:h:m:s]: 00:197:17:03:50
Block: 1117801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141116 RingCT/type: yes/0
Extra: 0105a7d389cafd7da0998990ce123e3d8b84b8c6d9e71695339a9c28aa0153d7e7021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fc178e806b5e8002db533bf800e5097b45a08dff77ebfbfe479bfefc5bbfd9d 0.600000000000 1598768 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": 1117811, "vin": [ { "gen": { "height": 1117801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fc178e806b5e8002db533bf800e5097b45a08dff77ebfbfe479bfefc5bbfd9d" } } ], "extra": [ 1, 5, 167, 211, 137, 202, 253, 125, 160, 153, 137, 144, 206, 18, 62, 61, 139, 132, 184, 198, 217, 231, 22, 149, 51, 154, 156, 40, 170, 1, 83, 215, 231, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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