Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcf25c9098f0b921d729533ada3db03eae0071c0fd4d84799d832bde5e95c16c

Tx prefix hash: 5dea9e57f13020648eea08ae9c4aa16f9673a967bede9f92a28e850af707cb84
Tx public key: 8fe0ebe7e17df285234d7d4ca19249f4578e131194800bdc09228a027ce3c55d
Timestamp: 1735624583 Timestamp [UCT]: 2024-12-31 05:56:23 Age [y:d:h:m:s]: 00:323:13:12:36
Block: 1186959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228763 RingCT/type: yes/0
Extra: 018fe0ebe7e17df285234d7d4ca19249f4578e131194800bdc09228a027ce3c55d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d21da9bd0e642d4b7f4aaf4fb19d1d6422bc457db8b29922ab64706dd818fa78 0.600000000000 1673444 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": 1186969, "vin": [ { "gen": { "height": 1186959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d21da9bd0e642d4b7f4aaf4fb19d1d6422bc457db8b29922ab64706dd818fa78" } } ], "extra": [ 1, 143, 224, 235, 231, 225, 125, 242, 133, 35, 77, 125, 76, 161, 146, 73, 244, 87, 142, 19, 17, 148, 128, 11, 220, 9, 34, 138, 2, 124, 227, 197, 93, 2, 17, 0, 0, 0, 3, 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