Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdd65c981d3637149d62ac224dd236f9890e6eba103008c4f8afdc685a1d96af

Tx prefix hash: e3b706f37e5e0b8af0ff10c5b5c9bd25c613416951ed92f42b21d03085a78f61
Tx public key: f2f92e2174a8d1332b715c05e8d19a284f24e5488a1358fc4cadbb777b739d14
Timestamp: 1727314352 Timestamp [UCT]: 2024-09-26 01:32:32 Age [y:d:h:m:s]: 00:149:12:05:27
Block: 1118194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106623 RingCT/type: yes/0
Extra: 01f2f92e2174a8d1332b715c05e8d19a284f24e5488a1358fc4cadbb777b739d14021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67a02a1301c4acd95a837b9aea8fa0ff5523c601b13ad482106d283fa45227a8 0.600000000000 1599301 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": 1118204, "vin": [ { "gen": { "height": 1118194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67a02a1301c4acd95a837b9aea8fa0ff5523c601b13ad482106d283fa45227a8" } } ], "extra": [ 1, 242, 249, 46, 33, 116, 168, 209, 51, 43, 113, 92, 5, 232, 209, 154, 40, 79, 36, 229, 72, 138, 19, 88, 252, 76, 173, 187, 119, 123, 115, 157, 20, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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