Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce3db0ccf1e51e8b6fc64fcd76524a3cc0b1f96e4c083fe6d13a5eb9ebde8bb

Tx prefix hash: f986b5622421463da801fa5bede61500af4280a899de5ce8fe852425e7e55114
Tx public key: a8aeb8e1e4e2e994746781d5fe816fb377e8c0dfb866a72cd08ca1911242a470
Timestamp: 1734914194 Timestamp [UCT]: 2024-12-23 00:36:34 Age [y:d:h:m:s]: 00:097:23:52:47
Block: 1181117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69782 RingCT/type: yes/0
Extra: 01a8aeb8e1e4e2e994746781d5fe816fb377e8c0dfb866a72cd08ca1911242a470021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae0dfb86ac7075071d6e6c7afc16faa7de6858860c376526e40c9b4a29b33598 0.600000000000 1667532 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": 1181127, "vin": [ { "gen": { "height": 1181117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae0dfb86ac7075071d6e6c7afc16faa7de6858860c376526e40c9b4a29b33598" } } ], "extra": [ 1, 168, 174, 184, 225, 228, 226, 233, 148, 116, 103, 129, 213, 254, 129, 111, 179, 119, 232, 192, 223, 184, 102, 167, 44, 208, 140, 161, 145, 18, 66, 164, 112, 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