Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8be9665eb0d25f3fa2ecf7a974ea2eef9779eb061ada71573b891cf30b1a0cef

Tx prefix hash: 0b00642695f4ef32378639cfcc0857407e496d02b86b86f0a6cf12bc1fa39bed
Tx public key: 96682275e225ecd46dd1178e3181d918d82eee0a68f0d52997978dc753a2034b
Timestamp: 1576424258 Timestamp [UCT]: 2019-12-15 15:37:38 Age [y:d:h:m:s]: 05:018:23:37:11
Block: 27303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160656 RingCT/type: yes/0
Extra: 0196682275e225ecd46dd1178e3181d918d82eee0a68f0d52997978dc753a2034b0211000000099159db1e000000000000000000

1 output(s) for total of 498.350264641000 dcy

stealth address amount amount idx
00: b0b7b37a794ceae0363cbd0cf60161f8190202f3f4dd6c243ea520f777f2cbe1 498.350264641000 45299 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": 27313, "vin": [ { "gen": { "height": 27303 } } ], "vout": [ { "amount": 498350264641, "target": { "key": "b0b7b37a794ceae0363cbd0cf60161f8190202f3f4dd6c243ea520f777f2cbe1" } } ], "extra": [ 1, 150, 104, 34, 117, 226, 37, 236, 212, 109, 209, 23, 142, 49, 129, 217, 24, 216, 46, 238, 10, 104, 240, 213, 41, 151, 151, 141, 199, 83, 162, 3, 75, 2, 17, 0, 0, 0, 9, 145, 89, 219, 30, 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