Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46fa5cb580c42ac78fa1a518e800ea3eb51635713022b10f4feea6712c65d9ff

Tx prefix hash: c349118acb12994b12af645a29675f1541f470f0d84a59dba146467297de96f5
Tx public key: 6a7bca298c97858b0dfd34200988f6c9e22cedf0a075a5a62eef5180669a5cdf
Timestamp: 1725607904 Timestamp [UCT]: 2024-09-06 07:31:44 Age [y:d:h:m:s]: 01:065:01:41:58
Block: 1104050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304930 RingCT/type: yes/0
Extra: 016a7bca298c97858b0dfd34200988f6c9e22cedf0a075a5a62eef5180669a5cdf02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caa3bf40d609c3d6df13db1495df05d4868e6cc0f7380b1efc4ef8457635d6c0 0.600000000000 1581109 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": 1104060, "vin": [ { "gen": { "height": 1104050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caa3bf40d609c3d6df13db1495df05d4868e6cc0f7380b1efc4ef8457635d6c0" } } ], "extra": [ 1, 106, 123, 202, 41, 140, 151, 133, 139, 13, 253, 52, 32, 9, 136, 246, 201, 226, 44, 237, 240, 160, 117, 165, 166, 46, 239, 81, 128, 102, 154, 92, 223, 2, 17, 0, 0, 0, 2, 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