Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fccdf9a80e52f756bef0ead69e0e026e9745cae25002d0159055993d9eb4b96

Tx prefix hash: a6025e0d7f935e1d8843f6f6ca004c35daf4fb44d7d7f6fc6d45cc7bc13f8a36
Tx public key: 3aa8ef6999032611c70df1e85b3babbcd21759b2eba482360911dca9e57dc142
Timestamp: 1737681746 Timestamp [UCT]: 2025-01-24 01:22:26 Age [y:d:h:m:s]: 00:147:20:54:52
Block: 1203954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105383 RingCT/type: yes/0
Extra: 013aa8ef6999032611c70df1e85b3babbcd21759b2eba482360911dca9e57dc14202110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c8fcd3eb65449adae0d0470731ffc84e80c1a21c9d7b17314c7b006e0d53d3e 0.600000000000 1690635 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": 1203964, "vin": [ { "gen": { "height": 1203954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c8fcd3eb65449adae0d0470731ffc84e80c1a21c9d7b17314c7b006e0d53d3e" } } ], "extra": [ 1, 58, 168, 239, 105, 153, 3, 38, 17, 199, 13, 241, 232, 91, 59, 171, 188, 210, 23, 89, 178, 235, 164, 130, 54, 9, 17, 220, 169, 229, 125, 193, 66, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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