Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd56eed52e4e58ba0739e517e14e4b15ccbfe976a6909c651942f632060f735d

Tx prefix hash: 9097482b58dff5f9187312c7846b0de69a8015e503b0b2923bc83e133a3fd71b
Tx public key: 3c266be60abacac836a7b74a248a7dd9e19813382d3a9fb069a256455eae4a22
Timestamp: 1740867854 Timestamp [UCT]: 2025-03-01 22:24:14 Age [y:d:h:m:s]: 00:211:20:29:43
Block: 1230092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149093 RingCT/type: yes/0
Extra: 013c266be60abacac836a7b74a248a7dd9e19813382d3a9fb069a256455eae4a2202110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fc8cbb462931294a7b624f2486002a9d3a34690b03af72a4fa0d1cfa826d996 0.600000000000 1716987 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": 1230102, "vin": [ { "gen": { "height": 1230092 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fc8cbb462931294a7b624f2486002a9d3a34690b03af72a4fa0d1cfa826d996" } } ], "extra": [ 1, 60, 38, 107, 230, 10, 186, 202, 200, 54, 167, 183, 74, 36, 138, 125, 217, 225, 152, 19, 56, 45, 58, 159, 176, 105, 162, 86, 69, 94, 174, 74, 34, 2, 17, 0, 0, 0, 10, 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