Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1845b17f397fc2e6e7035eb0243b3f9a9a63691748a284253291e1c6d53ec1f3

Tx prefix hash: ac5f4b09f9183e5969b24dd8b2f262575cea8d73d6d93b91d31f66b49f803be6
Tx public key: 97ac1bfe9530865e605dc5573c1a6e735824d0594598f8f002afa29d1d5bc946
Timestamp: 1583851508 Timestamp [UCT]: 2020-03-10 14:45:08 Age [y:d:h:m:s]: 05:236:07:25:28
Block: 79792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1322423 RingCT/type: yes/0
Extra: 0197ac1bfe9530865e605dc5573c1a6e735824d0594598f8f002afa29d1d5bc94602110000000678e4872e000000000000000000

1 output(s) for total of 333.900270600000 dcy

stealth address amount amount idx
00: 4017edc3d96f754bf92beba0bc0c604ef28bdc3a4941863cc33d6dcdd444f032 333.900270600000 146002 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": 79802, "vin": [ { "gen": { "height": 79792 } } ], "vout": [ { "amount": 333900270600, "target": { "key": "4017edc3d96f754bf92beba0bc0c604ef28bdc3a4941863cc33d6dcdd444f032" } } ], "extra": [ 1, 151, 172, 27, 254, 149, 48, 134, 94, 96, 93, 197, 87, 60, 26, 110, 115, 88, 36, 208, 89, 69, 152, 248, 240, 2, 175, 162, 157, 29, 91, 201, 70, 2, 17, 0, 0, 0, 6, 120, 228, 135, 46, 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