Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80ef18eb02f9e9a392e0a827a151bb005292cc4d884b58345c390fb7172a4e0d

Tx prefix hash: 869b70b768701bbfda15663e5724863b0961e9fb5c07ba96762e9fe4db9c6752
Tx public key: 652100c0f64dcfd05948a784d369b4e8ce6f4e3d4a5b59a5f22619db5a2b3653
Timestamp: 1579232604 Timestamp [UCT]: 2020-01-17 03:43:24 Age [y:d:h:m:s]: 05:058:22:04:52
Block: 47231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1192289 RingCT/type: yes/0
Extra: 01652100c0f64dcfd05948a784d369b4e8ce6f4e3d4a5b59a5f22619db5a2b3653021100000005d81c26c0000000000000000000

1 output(s) for total of 428.067676344000 dcy

stealth address amount amount idx
00: 24c34ca37a6e0ae2f4fe9ab99ccf5bcc49b7b06b836dc059be789bc021254a54 428.067676344000 87273 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": 47241, "vin": [ { "gen": { "height": 47231 } } ], "vout": [ { "amount": 428067676344, "target": { "key": "24c34ca37a6e0ae2f4fe9ab99ccf5bcc49b7b06b836dc059be789bc021254a54" } } ], "extra": [ 1, 101, 33, 0, 192, 246, 77, 207, 208, 89, 72, 167, 132, 211, 105, 180, 232, 206, 111, 78, 61, 74, 91, 89, 165, 242, 38, 25, 219, 90, 43, 54, 83, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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