Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32f4378848f5675d0fe6676eaeb306ec8d5c5856a7d3bbccf3186b9384f2787a

Tx prefix hash: 5b382fd52ea6b9861d9c4faf2a3c554f1e3d5fb0383f1d39f5ab035550c6023d
Tx public key: 862853f2ea66841d0264bc70b6a2f5cab856a523fa67ac7eb782953387299c1e
Timestamp: 1581820723 Timestamp [UCT]: 2020-02-16 02:38:43 Age [y:d:h:m:s]: 04:284:17:50:39
Block: 65724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095913 RingCT/type: yes/0
Extra: 01862853f2ea66841d0264bc70b6a2f5cab856a523fa67ac7eb782953387299c1e021100000001c71d3ff9000000000000000000

1 output(s) for total of 371.731971164000 dcy

stealth address amount amount idx
00: 375b9bae14837e4c57b3595e2e1f3e468761e37a985f1aafc148645c279f6990 371.731971164000 121295 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": 65734, "vin": [ { "gen": { "height": 65724 } } ], "vout": [ { "amount": 371731971164, "target": { "key": "375b9bae14837e4c57b3595e2e1f3e468761e37a985f1aafc148645c279f6990" } } ], "extra": [ 1, 134, 40, 83, 242, 234, 102, 132, 29, 2, 100, 188, 112, 182, 162, 245, 202, 184, 86, 165, 35, 250, 103, 172, 126, 183, 130, 149, 51, 135, 41, 156, 30, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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