Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 247d90799c2e5d2f7bceb4985a63eb3463b2efd42d4909b4e71767b332dca4ec

Tx prefix hash: 08697e96a1bcdbbd0ba9019ea2528dda3ea514366be6f4d229bac1aae1f8f9ee
Tx public key: 3ccd9cc943f605ecbc3f2500226b947e7d0fd2fa7f4c8be688c53041b059fe37
Timestamp: 1705201335 Timestamp [UCT]: 2024-01-14 03:02:15 Age [y:d:h:m:s]: 01:075:09:11:18
Block: 934838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314989 RingCT/type: yes/0
Extra: 013ccd9cc943f605ecbc3f2500226b947e7d0fd2fa7f4c8be688c53041b059fe370211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcdd4f091389a23f14f500c3645eac3efb4c1989f0843799191721f9c8277a60 0.600000000000 1392854 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": 934848, "vin": [ { "gen": { "height": 934838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcdd4f091389a23f14f500c3645eac3efb4c1989f0843799191721f9c8277a60" } } ], "extra": [ 1, 60, 205, 156, 201, 67, 246, 5, 236, 188, 63, 37, 0, 34, 107, 148, 126, 125, 15, 210, 250, 127, 76, 139, 230, 136, 197, 48, 65, 176, 89, 254, 55, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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