Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f90fefb407a5514d5ddc0baa33ee522c296080167a730baeaffd8bcf128d47f8

Tx prefix hash: c1f946ee090b5667f81d934d4a9c7c3b157665fe81b2bd6f1ca09fc80a1ed41c
Tx public key: e90b2b6ebaea8aec577c92a7f7f62dcefa73b175dc975ea711d44bdb6b2b1e6e
Timestamp: 1726161247 Timestamp [UCT]: 2024-09-12 17:14:07 Age [y:d:h:m:s]: 00:101:01:38:35
Block: 1108624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72320 RingCT/type: yes/0
Extra: 01e90b2b6ebaea8aec577c92a7f7f62dcefa73b175dc975ea711d44bdb6b2b1e6e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70b69796164efa73c0b92326d9cabbdcc726ceee20f6d7a4379ff007e846f2b2 0.600000000000 1586587 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": 1108634, "vin": [ { "gen": { "height": 1108624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70b69796164efa73c0b92326d9cabbdcc726ceee20f6d7a4379ff007e846f2b2" } } ], "extra": [ 1, 233, 11, 43, 110, 186, 234, 138, 236, 87, 124, 146, 167, 247, 246, 45, 206, 250, 115, 177, 117, 220, 151, 94, 167, 17, 212, 75, 219, 107, 43, 30, 110, 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