Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48b6fbd1dfe8098a6e66e46d01278667f4926e489822b418bdb79b461ca297e0

Tx prefix hash: d9ba95d1d4ab70e24b9b3eda48c2ba183520519befdd8fc682db4e5ddc1deba6
Tx public key: 2b25976b938db34ed6cdfaf8f8d648ce888dbcbd14ddca2af5a492e713d59f49
Timestamp: 1730104809 Timestamp [UCT]: 2024-10-28 08:40:09 Age [y:d:h:m:s]: 00:085:15:15:58
Block: 1141260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61217 RingCT/type: yes/0
Extra: 012b25976b938db34ed6cdfaf8f8d648ce888dbcbd14ddca2af5a492e713d59f49021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58a89f628921802dbfb0b5184b39892cfa7d3874376aece88dfdc9d3ce3d7b5f 0.600000000000 1625067 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": 1141270, "vin": [ { "gen": { "height": 1141260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58a89f628921802dbfb0b5184b39892cfa7d3874376aece88dfdc9d3ce3d7b5f" } } ], "extra": [ 1, 43, 37, 151, 107, 147, 141, 179, 78, 214, 205, 250, 248, 248, 214, 72, 206, 136, 141, 188, 189, 20, 221, 202, 42, 245, 164, 146, 231, 19, 213, 159, 73, 2, 17, 0, 0, 0, 2, 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