Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77416df44b27cf749b9d8af41ec1a4335477fe1614d29367c043c669d7ca1936

Tx prefix hash: ad3efc709a1b7d37415ec5d8f234efd7d10f3fff93c0c6a324e055dfae4d4efb
Tx public key: f984677b61a50082e72412f81c3ca84558f6373bfe738c3a84e65f4bf38dcff2
Timestamp: 1722820319 Timestamp [UCT]: 2024-08-05 01:11:59 Age [y:d:h:m:s]: 00:157:04:36:05
Block: 1080927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112472 RingCT/type: yes/0
Extra: 01f984677b61a50082e72412f81c3ca84558f6373bfe738c3a84e65f4bf38dcff2021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 336e6f38350158533084c5c89374f3d1e938af6fd118625d941921dad9afc0e7 0.600000000000 1554478 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": 1080937, "vin": [ { "gen": { "height": 1080927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "336e6f38350158533084c5c89374f3d1e938af6fd118625d941921dad9afc0e7" } } ], "extra": [ 1, 249, 132, 103, 123, 97, 165, 0, 130, 231, 36, 18, 248, 28, 60, 168, 69, 88, 246, 55, 59, 254, 115, 140, 58, 132, 230, 95, 75, 243, 141, 207, 242, 2, 17, 0, 0, 0, 6, 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