Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e94f0cc43e68dbe79aca98e2b36b9d65de49442f3021d9616d18a2e049c7351

Tx prefix hash: b4de89948ab5eadb611270c6d1175acb2d4359a0e5c0032fc0b027639a2829d9
Tx public key: a9e36f8b99f8dfb4605dcf533cac190e91840a7de1194b1dc225e8f33d91bd9e
Timestamp: 1577531220 Timestamp [UCT]: 2019-12-28 11:07:00 Age [y:d:h:m:s]: 05:042:23:33:45
Block: 33423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1180603 RingCT/type: yes/0
Extra: 01a9e36f8b99f8dfb4605dcf533cac190e91840a7de1194b1dc225e8f33d91bd9e02110000000d8a2ee0d9000000000000000000

1 output(s) for total of 475.616139752000 dcy

stealth address amount amount idx
00: a349109b1ecb13b2119b289906150a4a99a6957cb705c754906eeeb0635f13e4 475.616139752000 55960 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": 33433, "vin": [ { "gen": { "height": 33423 } } ], "vout": [ { "amount": 475616139752, "target": { "key": "a349109b1ecb13b2119b289906150a4a99a6957cb705c754906eeeb0635f13e4" } } ], "extra": [ 1, 169, 227, 111, 139, 153, 248, 223, 180, 96, 93, 207, 83, 60, 172, 25, 14, 145, 132, 10, 125, 225, 25, 75, 29, 194, 37, 232, 243, 61, 145, 189, 158, 2, 17, 0, 0, 0, 13, 138, 46, 224, 217, 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