Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2243ed165ea22a6358884780a4c6d7579ba8f26311409b59627204c146b5085

Tx prefix hash: a85ac813894ec94f06123ed74106ae6d879da1f73b3ce94eae517bd2a69f0c92
Tx public key: fcdbfa217451b00a44e570650ccc86b463caae6b9ac9784cf534f7913ac16cb4
Timestamp: 1577710313 Timestamp [UCT]: 2019-12-30 12:51:53 Age [y:d:h:m:s]: 05:000:06:29:42
Block: 35028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150182 RingCT/type: yes/0
Extra: 01fcdbfa217451b00a44e570650ccc86b463caae6b9ac9784cf534f7913ac16cb40211000000028a2ee0d9000000000000000000

1 output(s) for total of 469.827626293000 dcy

stealth address amount amount idx
00: fc7f1d112f7218b52b9e19ba3b51364bc5cf18dd888f9e06a6d3140801f8831e 469.827626293000 59013 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": 35038, "vin": [ { "gen": { "height": 35028 } } ], "vout": [ { "amount": 469827626293, "target": { "key": "fc7f1d112f7218b52b9e19ba3b51364bc5cf18dd888f9e06a6d3140801f8831e" } } ], "extra": [ 1, 252, 219, 250, 33, 116, 81, 176, 10, 68, 229, 112, 101, 12, 204, 134, 180, 99, 202, 174, 107, 154, 201, 120, 76, 245, 52, 247, 145, 58, 193, 108, 180, 2, 17, 0, 0, 0, 2, 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