Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4618d7d7b591bd88e26989ed675c79a4c12f175271eb119a4d71b806b46afdd

Tx prefix hash: 0943d5f3921c079d7813d50a4dadab6397eb5c1155c7f59f53851ac2a07de986
Tx public key: 70407c89cad0bf17e066ef02ae12e5c509f11ea2759adaa88e449909e8a092ed
Timestamp: 1577587544 Timestamp [UCT]: 2019-12-29 02:45:44 Age [y:d:h:m:s]: 05:066:20:43:10
Block: 33992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1197572 RingCT/type: yes/0
Extra: 0170407c89cad0bf17e066ef02ae12e5c509f11ea2759adaa88e449909e8a092ed02110000000cad433a0b000000000000000000

1 output(s) for total of 473.564077666000 dcy

stealth address amount amount idx
00: ab7ea5edade82feab175337adc422cb33b50a6e33fe8cceb7e2960ca6ee267df 473.564077666000 57169 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": 34002, "vin": [ { "gen": { "height": 33992 } } ], "vout": [ { "amount": 473564077666, "target": { "key": "ab7ea5edade82feab175337adc422cb33b50a6e33fe8cceb7e2960ca6ee267df" } } ], "extra": [ 1, 112, 64, 124, 137, 202, 208, 191, 23, 224, 102, 239, 2, 174, 18, 229, 197, 9, 241, 30, 162, 117, 154, 218, 168, 142, 68, 153, 9, 232, 160, 146, 237, 2, 17, 0, 0, 0, 12, 173, 67, 58, 11, 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