Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a7af6d4752eb0d4a6d4de04c3cf3db55938515ba7262258c0c6714faaf0d80a

Tx prefix hash: 5374a46e3739beb3edd041ff156ceaa0685332d9e3b42dc63ff9ab8d708ee20f
Tx public key: 679e9613a4aa686f6d4c8e6164ee86aa36d8591ad77ac179eda4b26f71128e31
Timestamp: 1582798653 Timestamp [UCT]: 2020-02-27 10:17:33 Age [y:d:h:m:s]: 05:251:14:54:39
Block: 72576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1331876 RingCT/type: yes/0
Extra: 01679e9613a4aa686f6d4c8e6164ee86aa36d8591ad77ac179eda4b26f71128e31021100000002724f989b000000000000000000

1 output(s) for total of 352.798219097000 dcy

stealth address amount amount idx
00: a1b7c12158892c5362f593302a959e6113bc7f0cef0c87dd60925f1029c5b4fe 352.798219097000 134099 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": 72586, "vin": [ { "gen": { "height": 72576 } } ], "vout": [ { "amount": 352798219097, "target": { "key": "a1b7c12158892c5362f593302a959e6113bc7f0cef0c87dd60925f1029c5b4fe" } } ], "extra": [ 1, 103, 158, 150, 19, 164, 170, 104, 111, 109, 76, 142, 97, 100, 238, 134, 170, 54, 216, 89, 26, 215, 122, 193, 121, 237, 164, 178, 111, 113, 18, 142, 49, 2, 17, 0, 0, 0, 2, 114, 79, 152, 155, 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