Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43ace66ecc0e95ba636a66a661ab08445c8cbd924404b808894f3cbb30f688cb

Tx prefix hash: e56b2e01f8abcc5a3f020a4063fb89cd9a0d1f9a38cc1717f6efb5088e3c739f
Tx public key: 1cb63b086da289ac90af61e77ae811071f4a3d80d2a88c05530f288a42806e60
Timestamp: 1721264603 Timestamp [UCT]: 2024-07-18 01:03:23 Age [y:d:h:m:s]: 00:259:19:15:41
Block: 1068057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185576 RingCT/type: yes/0
Extra: 011cb63b086da289ac90af61e77ae811071f4a3d80d2a88c05530f288a42806e6002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bd6b63b3f635f652ea8504cf72935d978820c68327508d86e09b61e5e15d6ce 0.600000000000 1539050 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": 1068067, "vin": [ { "gen": { "height": 1068057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bd6b63b3f635f652ea8504cf72935d978820c68327508d86e09b61e5e15d6ce" } } ], "extra": [ 1, 28, 182, 59, 8, 109, 162, 137, 172, 144, 175, 97, 231, 122, 232, 17, 7, 31, 74, 61, 128, 210, 168, 140, 5, 83, 15, 40, 138, 66, 128, 110, 96, 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