Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49605845f76449e7a326fa3691a9adaa3d3b701a6e0b5017f709ddf1ec7b1f6b

Tx prefix hash: a411e4b7732c85ce88a4af6fc21e0a45cedad3118d5841b42801c8aecc5503e7
Tx public key: a2e45d27cf231ab7d376a9a7ee295fa7040544f4159dd18ece15c7a19762f301
Timestamp: 1735593260 Timestamp [UCT]: 2024-12-30 21:14:20 Age [y:d:h:m:s]: 00:351:14:28:05
Block: 1186699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248845 RingCT/type: yes/0
Extra: 01a2e45d27cf231ab7d376a9a7ee295fa7040544f4159dd18ece15c7a19762f301021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a60a665d2d432964342ba631d66e1ee9886c3c53ff7b9a670f8f845ef5f23da5 0.600000000000 1673184 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": 1186709, "vin": [ { "gen": { "height": 1186699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a60a665d2d432964342ba631d66e1ee9886c3c53ff7b9a670f8f845ef5f23da5" } } ], "extra": [ 1, 162, 228, 93, 39, 207, 35, 26, 183, 211, 118, 169, 167, 238, 41, 95, 167, 4, 5, 68, 244, 21, 157, 209, 142, 206, 21, 199, 161, 151, 98, 243, 1, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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