Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 619d964d9a45f35b6532d938e9a24b44cd8fb46e483afb56e2a931a54cbbe4d1

Tx prefix hash: c6690abf7e13db8806ce24ec460c141230fa9bceb70d445e205c5b466ca6cd7f
Tx public key: 7f9d6db57c24a41cea3667f238662cfaeff02a988ce5f5cd78b08d9780c73b0a
Timestamp: 1720210807 Timestamp [UCT]: 2024-07-05 20:20:07 Age [y:d:h:m:s]: 00:254:05:36:32
Block: 1059295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181652 RingCT/type: yes/0
Extra: 017f9d6db57c24a41cea3667f238662cfaeff02a988ce5f5cd78b08d9780c73b0a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 255efba09c8211946bb18602d22c857e4fdb50fa0d9c6c4e2f7b80e031f2ad0b 0.600000000000 1529762 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": 1059305, "vin": [ { "gen": { "height": 1059295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "255efba09c8211946bb18602d22c857e4fdb50fa0d9c6c4e2f7b80e031f2ad0b" } } ], "extra": [ 1, 127, 157, 109, 181, 124, 36, 164, 28, 234, 54, 103, 242, 56, 102, 44, 250, 239, 240, 42, 152, 140, 229, 245, 205, 120, 176, 141, 151, 128, 199, 59, 10, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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