Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85fcb72ccf516c333b64f63251cbc6b8072d2c1926ad389784d5e9c96b9baabe

Tx prefix hash: aaba31ee7dbe0b8e91a020aee373296f744111136955409998d87a5a01b0a586
Tx public key: 1e89099e73f0f117beba6891567f67fc62e063ae575a817f8cf5ef1e1d41162f
Timestamp: 1625623726 Timestamp [UCT]: 2021-07-07 02:08:46 Age [y:d:h:m:s]: 04:121:01:49:09
Block: 289398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115134 RingCT/type: yes/0
Extra: 011e89099e73f0f117beba6891567f67fc62e063ae575a817f8cf5ef1e1d41162f02110000001b4b22f71d000000000000000000

1 output(s) for total of 67.470251397000 dcy

stealth address amount amount idx
00: 7bc29eb1d27616cef050eb338a34fd92e5175884fa15ada4ee9b1715136d8d64 67.470251397000 606106 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": 289408, "vin": [ { "gen": { "height": 289398 } } ], "vout": [ { "amount": 67470251397, "target": { "key": "7bc29eb1d27616cef050eb338a34fd92e5175884fa15ada4ee9b1715136d8d64" } } ], "extra": [ 1, 30, 137, 9, 158, 115, 240, 241, 23, 190, 186, 104, 145, 86, 127, 103, 252, 98, 224, 99, 174, 87, 90, 129, 127, 140, 245, 239, 30, 29, 65, 22, 47, 2, 17, 0, 0, 0, 27, 75, 34, 247, 29, 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