Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acfd376799af2cbad2db43e52412e313c6f1ee65af0137a2775144caecadf363

Tx prefix hash: a8243ee35c723d64d061c01dd923a212fff9dc2a278f10f3025f51e293d7513a
Tx public key: c931e99a0ff600c7cf9ef81fd277eb5806fc6001269d4bc9969a02c5748e9654
Timestamp: 1574261757 Timestamp [UCT]: 2019-11-20 14:55:57 Age [y:d:h:m:s]: 05:346:08:17:08
Block: 13285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1388253 RingCT/type: yes/0
Extra: 01c931e99a0ff600c7cf9ef81fd277eb5806fc6001269d4bc9969a02c5748e965402110000000366a80d00000000000000000000

1 output(s) for total of 554.602939132000 dcy

stealth address amount amount idx
00: c66c5954202e4621c7f0aa2378e16091a7b25745318c3b52d341550ea0266293 554.602939132000 15534 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": 13295, "vin": [ { "gen": { "height": 13285 } } ], "vout": [ { "amount": 554602939132, "target": { "key": "c66c5954202e4621c7f0aa2378e16091a7b25745318c3b52d341550ea0266293" } } ], "extra": [ 1, 201, 49, 233, 154, 15, 246, 0, 199, 207, 158, 248, 31, 210, 119, 235, 88, 6, 252, 96, 1, 38, 157, 75, 201, 150, 154, 2, 197, 116, 142, 150, 84, 2, 17, 0, 0, 0, 3, 102, 168, 13, 0, 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