Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f26e35887241a38bd911931e81f53e1dd47f8898e7a7d920dd4f2b53d7650a1

Tx prefix hash: f8579c2b092b0c48154ee3bd9c3f056a9ebb089798d7e2900a452f0516d3cb94
Tx public key: 49564e46a3b82353d1ce3515e5ee5dae84b9dc19a7c686ce6b5d9914744dc7da
Timestamp: 1729619357 Timestamp [UCT]: 2024-10-22 17:49:17 Age [y:d:h:m:s]: 00:142:18:27:00
Block: 1137268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101853 RingCT/type: yes/0
Extra: 0149564e46a3b82353d1ce3515e5ee5dae84b9dc19a7c686ce6b5d9914744dc7da021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4dd3d03af13b8dfae9c2df3420c338916d97ac6e7263a2d55ecf4b461b1fb94d 0.600000000000 1620727 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": 1137278, "vin": [ { "gen": { "height": 1137268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4dd3d03af13b8dfae9c2df3420c338916d97ac6e7263a2d55ecf4b461b1fb94d" } } ], "extra": [ 1, 73, 86, 78, 70, 163, 184, 35, 83, 209, 206, 53, 21, 229, 238, 93, 174, 132, 185, 220, 25, 167, 198, 134, 206, 107, 93, 153, 20, 116, 77, 199, 218, 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