Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a429ab74385b91a5fcc933aa93c69343ee65d7a9418b986a57d47f9812f9b1e7

Tx prefix hash: 8223103151c14974815f30c39e5469b76f21e4e600968b4973508af2af701cc1
Tx public key: 4a397c71965d4bd505842e1a8097e965ef7c5f4cadb92377e1d940c063360685
Timestamp: 1598184918 Timestamp [UCT]: 2020-08-23 12:15:18 Age [y:d:h:m:s]: 05:073:14:12:25
Block: 128850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1275629 RingCT/type: yes/0
Extra: 014a397c71965d4bd505842e1a8097e965ef7c5f4cadb92377e1d940c063360685021100000007d81c26c0000000000000000000

1 output(s) for total of 229.650387333000 dcy

stealth address amount amount idx
00: ae296fb5e7580a8c2e638d81a8fa796a89c1158f78012f6f75a378ef833f0edf 229.650387333000 216332 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": 128860, "vin": [ { "gen": { "height": 128850 } } ], "vout": [ { "amount": 229650387333, "target": { "key": "ae296fb5e7580a8c2e638d81a8fa796a89c1158f78012f6f75a378ef833f0edf" } } ], "extra": [ 1, 74, 57, 124, 113, 150, 93, 75, 213, 5, 132, 46, 26, 128, 151, 233, 101, 239, 124, 95, 76, 173, 185, 35, 119, 225, 217, 64, 192, 99, 54, 6, 133, 2, 17, 0, 0, 0, 7, 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