Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec8bc4c091de906a03afdf4ece64486d520aac9376efb48754d7ef5345dac1a

Tx prefix hash: c95f9b446584a710019a5d6532b7f329481249effe1e2c2821fd4be1276d5328
Tx public key: ae0aa60d854ed4d6730a972e49e98f5e99bd609b6e3421a15232704aaab1f78f
Timestamp: 1674076487 Timestamp [UCT]: 2023-01-18 21:14:47 Age [y:d:h:m:s]: 02:037:15:28:35
Block: 677688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548533 RingCT/type: yes/0
Extra: 01ae0aa60d854ed4d6730a972e49e98f5e99bd609b6e3421a15232704aaab1f78f02110000000175e3f0e9000000000000000000

1 output(s) for total of 3.487693246000 dcy

stealth address amount amount idx
00: 0b4e66465d5e15f7e1c8e3e91d3a27c3a180760f3da1274b02109d4b9e5277f1 3.487693246000 1119477 of 0

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": 677698, "vin": [ { "gen": { "height": 677688 } } ], "vout": [ { "amount": 3487693246, "target": { "key": "0b4e66465d5e15f7e1c8e3e91d3a27c3a180760f3da1274b02109d4b9e5277f1" } } ], "extra": [ 1, 174, 10, 166, 13, 133, 78, 212, 214, 115, 10, 151, 46, 73, 233, 143, 94, 153, 189, 96, 155, 110, 52, 33, 161, 82, 50, 112, 74, 170, 177, 247, 143, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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