Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3abb2eb3a0f302aa5c717f89ae86973316e5253bf966c6a349d7046e3594b387

Tx prefix hash: eebee912a2e9a2fa24f5f9f8075713cc628ca639006b0b0899251b895419bb1d
Tx public key: 34d8345bc1836fa6e7a0fce2e0ae59854a1ddf3dd66e2450f1d5425a64ace9b1
Timestamp: 1722568386 Timestamp [UCT]: 2024-08-02 03:13:06 Age [y:d:h:m:s]: 00:252:18:02:07
Block: 1078850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180548 RingCT/type: yes/0
Extra: 0134d8345bc1836fa6e7a0fce2e0ae59854a1ddf3dd66e2450f1d5425a64ace9b102110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ee811181133d86ba874dfd294535f3c3203594194a498f2afc2173c51f5b65c 0.600000000000 1551555 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": 1078860, "vin": [ { "gen": { "height": 1078850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ee811181133d86ba874dfd294535f3c3203594194a498f2afc2173c51f5b65c" } } ], "extra": [ 1, 52, 216, 52, 91, 193, 131, 111, 166, 231, 160, 252, 226, 224, 174, 89, 133, 74, 29, 223, 61, 214, 110, 36, 80, 241, 213, 66, 90, 100, 172, 233, 177, 2, 17, 0, 0, 0, 7, 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