Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3888b0e8ecaa0680b44d7346165f8a4f6489889f99afab42b773114c24f2a20

Tx prefix hash: 2da104d408a5c2327991c00ea7ca44bbe0679a2b783c559033648513f8f1df1c
Tx public key: 6c6be568c25fd785de0421697585e9c4da788faea297eba7c3e091b9be1c46a0
Timestamp: 1704317916 Timestamp [UCT]: 2024-01-03 21:38:36 Age [y:d:h:m:s]: 01:279:01:06:23
Block: 927558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458191 RingCT/type: yes/0
Extra: 016c6be568c25fd785de0421697585e9c4da788faea297eba7c3e091b9be1c46a002110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c079deb958e0d6fc32aa58b39889cc24ebf95f0deee8a5f45f118a8fd987e48 0.600000000000 1385394 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": 927568, "vin": [ { "gen": { "height": 927558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c079deb958e0d6fc32aa58b39889cc24ebf95f0deee8a5f45f118a8fd987e48" } } ], "extra": [ 1, 108, 107, 229, 104, 194, 95, 215, 133, 222, 4, 33, 105, 117, 133, 233, 196, 218, 120, 143, 174, 162, 151, 235, 167, 195, 224, 145, 185, 190, 28, 70, 160, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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