Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fed673a96c9e1d871d2cb1f44d8781f67f41fb3042c4fa72cf1f4e0f0dd44570

Tx prefix hash: 1afa6e53403acb73ebaffa5f1eae2d06a4abcd5cf4385365398fe5cf53f53186
Tx public key: 3de6041fa6072983ddb123cc6c8ed96a82ee9e3d96cd79dcaed5160a803b9141
Timestamp: 1728748998 Timestamp [UCT]: 2024-10-12 16:03:18 Age [y:d:h:m:s]: 00:175:23:37:58
Block: 1130085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125556 RingCT/type: yes/0
Extra: 013de6041fa6072983ddb123cc6c8ed96a82ee9e3d96cd79dcaed5160a803b914102110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 566cf28796a521caf3019b6e77710ef540849d4d9ee9f5abf51a45c3cbb24d53 0.600000000000 1612956 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": 1130095, "vin": [ { "gen": { "height": 1130085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "566cf28796a521caf3019b6e77710ef540849d4d9ee9f5abf51a45c3cbb24d53" } } ], "extra": [ 1, 61, 230, 4, 31, 166, 7, 41, 131, 221, 177, 35, 204, 108, 142, 217, 106, 130, 238, 158, 61, 150, 205, 121, 220, 174, 213, 22, 10, 128, 59, 145, 65, 2, 17, 0, 0, 0, 1, 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