Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f8013034ed60a79646cddce8b4ec31008a4a58a41e36354c9336dab168110ee

Tx prefix hash: 019c5a3805cc4db7eb5e96b6630b742faebddbe7b46d00350056d5a33de43fe2
Tx public key: 5ea824aa738d8b8c1c2b29e9d05ef5de9cec3e1adf0f719de42116b9d9a7190a
Timestamp: 1699079830 Timestamp [UCT]: 2023-11-04 06:37:10 Age [y:d:h:m:s]: 01:224:21:51:15
Block: 884320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421686 RingCT/type: yes/0
Extra: 015ea824aa738d8b8c1c2b29e9d05ef5de9cec3e1adf0f719de42116b9d9a7190a02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.720909498000 dcy

stealth address amount amount idx
00: 382678518d724770a992a9e9ebc6fd7786f99485dfed1d63e40fa745485b246e 0.720909498000 1340057 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": 884330, "vin": [ { "gen": { "height": 884320 } } ], "vout": [ { "amount": 720909498, "target": { "key": "382678518d724770a992a9e9ebc6fd7786f99485dfed1d63e40fa745485b246e" } } ], "extra": [ 1, 94, 168, 36, 170, 115, 141, 139, 140, 28, 43, 41, 233, 208, 94, 245, 222, 156, 236, 62, 26, 223, 15, 113, 157, 228, 33, 22, 185, 217, 167, 25, 10, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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