Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5197df18a26ecbbcd7d8e11184872138acf9ad16cb5c738e17a4369c224b61c9

Tx prefix hash: cd88ba55b120f490d2855fa0dab79b9e26b4ef9dd92ed94f43c9f0f9aa4543c2
Tx public key: 71028afa02a862d062519da7e47a0b2418b19b32093e1980a63e36283375b455
Timestamp: 1578151370 Timestamp [UCT]: 2020-01-04 15:22:50 Age [y:d:h:m:s]: 04:319:05:00:37
Block: 38612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117307 RingCT/type: yes/0
Extra: 0171028afa02a862d062519da7e47a0b2418b19b32093e1980a63e36283375b4550211000000038a2ee0d9000000000000000000

1 output(s) for total of 457.154779961000 dcy

stealth address amount amount idx
00: 7c3b21e663bcf0fc33aea9dee990ff84db503fb667c3a9ec094993b59544c03e 457.154779961000 65963 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": 38622, "vin": [ { "gen": { "height": 38612 } } ], "vout": [ { "amount": 457154779961, "target": { "key": "7c3b21e663bcf0fc33aea9dee990ff84db503fb667c3a9ec094993b59544c03e" } } ], "extra": [ 1, 113, 2, 138, 250, 2, 168, 98, 208, 98, 81, 157, 167, 228, 122, 11, 36, 24, 177, 155, 50, 9, 62, 25, 128, 166, 62, 54, 40, 51, 117, 180, 85, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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