Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43067f6f54f37f6e94efb98e95d1d695beab52925715c69a93c2b3346ffff317

Tx prefix hash: 3efa49294451229a7c4b457b92bf076a3df2a56ebfa260013bb708f15a4ebae0
Tx public key: 089927ef9e86077772c1d48a8c8b07b2606d202b8aa8df2be2673991e5535121
Timestamp: 1582189346 Timestamp [UCT]: 2020-02-20 09:02:26 Age [y:d:h:m:s]: 05:349:05:32:48
Block: 68615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1400498 RingCT/type: yes/0
Extra: 01089927ef9e86077772c1d48a8c8b07b2606d202b8aa8df2be2673991e5535121021100000001c71d3ff9000000000000000000

1 output(s) for total of 363.622566053000 dcy

stealth address amount amount idx
00: a614ce8aed2f793c00f63a7fb108d44b6f770c06a4a533c74e1cb1dc458fd07f 363.622566053000 126508 of 0

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": 68625, "vin": [ { "gen": { "height": 68615 } } ], "vout": [ { "amount": 363622566053, "target": { "key": "a614ce8aed2f793c00f63a7fb108d44b6f770c06a4a533c74e1cb1dc458fd07f" } } ], "extra": [ 1, 8, 153, 39, 239, 158, 134, 7, 119, 114, 193, 212, 138, 140, 139, 7, 178, 96, 109, 32, 43, 138, 168, 223, 43, 226, 103, 57, 145, 229, 83, 81, 33, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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