Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfce502e0f6e5bbce816d0727b2b9e41b362bce9a8cf1dd3bc924af1d37572c0

Tx prefix hash: 89d8b0d3f1461718d70e07a9f6cd6debfc2f32eb67b46839521b96c648250e5c
Tx public key: cf701abac455022a01e913adaed5947999003f5d0ea147500a82e03550f7a5f6
Timestamp: 1574727223 Timestamp [UCT]: 2019-11-26 00:13:43 Age [y:d:h:m:s]: 05:170:20:03:29
Block: 17537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1264720 RingCT/type: yes/0
Extra: 01cf701abac455022a01e913adaed5947999003f5d0ea147500a82e03550f7a5f6021100000001f95225a5000000000000000000

1 output(s) for total of 536.900142813000 dcy

stealth address amount amount idx
00: 07979036ff9e4618eb1ae29bfe9c71d5bedcfe083417d45c80b250ba68f07e88 536.900142813000 25631 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": 17547, "vin": [ { "gen": { "height": 17537 } } ], "vout": [ { "amount": 536900142813, "target": { "key": "07979036ff9e4618eb1ae29bfe9c71d5bedcfe083417d45c80b250ba68f07e88" } } ], "extra": [ 1, 207, 112, 26, 186, 196, 85, 2, 42, 1, 233, 19, 173, 174, 213, 148, 121, 153, 0, 63, 93, 14, 161, 71, 80, 10, 130, 224, 53, 80, 247, 165, 246, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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