Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6ceb35bcd3f909e3212b4bccb6b4742ce7753b9d9546b84abf20dce02d43207

Tx prefix hash: 42d4d0a1ce0f085c0e5d0286bab7d558b6ddbd8040101a3691abc4407bce8bb0
Tx public key: 363433e230c61aa77f8be544b293b3d3bd5b4c05d6dc65fbd95ff3c8aa05959a
Timestamp: 1712462882 Timestamp [UCT]: 2024-04-07 04:08:02 Age [y:d:h:m:s]: 01:047:11:45:38
Block: 995034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294966 RingCT/type: yes/0
Extra: 01363433e230c61aa77f8be544b293b3d3bd5b4c05d6dc65fbd95ff3c8aa05959a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b12fdeeb150aa44f02a29eb3fc77a4b55957b0814eabdb65a5d171e0a0a8e954 0.600000000000 1455438 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": 995044, "vin": [ { "gen": { "height": 995034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b12fdeeb150aa44f02a29eb3fc77a4b55957b0814eabdb65a5d171e0a0a8e954" } } ], "extra": [ 1, 54, 52, 51, 226, 48, 198, 26, 167, 127, 139, 229, 68, 178, 147, 179, 211, 189, 91, 76, 5, 214, 220, 101, 251, 217, 95, 243, 200, 170, 5, 149, 154, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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