Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78cecfebd0437a7feaa5f339bb32f03f4da4ba4a545f8c4b3a33f686ac64fd64

Tx prefix hash: 7cfd5b3f40e135c8cbddb10aa2559c5108b5621bfe4488f0ac060eb361d0e7b2
Tx public key: 39fff48e2d4b214cc3cb9f47f4d0af6f6ff0ba8a7e2fb5fb54aba05e18553f3f
Timestamp: 1728408717 Timestamp [UCT]: 2024-10-08 17:31:57 Age [y:d:h:m:s]: 00:170:16:44:30
Block: 1127263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121785 RingCT/type: yes/0
Extra: 0139fff48e2d4b214cc3cb9f47f4d0af6f6ff0ba8a7e2fb5fb54aba05e18553f3f021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3caebdf5916a396bb6a5060f8526e87af8e7755babd90363725323cd40c7b32 0.600000000000 1610064 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": 1127273, "vin": [ { "gen": { "height": 1127263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3caebdf5916a396bb6a5060f8526e87af8e7755babd90363725323cd40c7b32" } } ], "extra": [ 1, 57, 255, 244, 142, 45, 75, 33, 76, 195, 203, 159, 71, 244, 208, 175, 111, 111, 240, 186, 138, 126, 47, 181, 251, 84, 171, 160, 94, 24, 85, 63, 63, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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