Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c55b925794ce749d351a90ecc62f412157baa505120f27a70dd11e6ef241c5c

Tx prefix hash: d40b9d167e0af6d67a1d08ad809892540b414e096d4f0aa654fb57fc8d6995d2
Tx public key: 55f29291427248c9e73cc8c7ce8849859501717a8bab1b4783f23fcc629a5321
Timestamp: 1576643686 Timestamp [UCT]: 2019-12-18 04:34:46 Age [y:d:h:m:s]: 05:342:14:12:27
Block: 28350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1390231 RingCT/type: yes/0
Extra: 0155f29291427248c9e73cc8c7ce8849859501717a8bab1b4783f23fcc629a532102110000005b9159db1e000000000000000000

1 output(s) for total of 494.385296643000 dcy

stealth address amount amount idx
00: fc9f7ec59a190179b9d864e2b6a448af068fe35641683fd0d9969a8a2cad79d2 494.385296643000 46894 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": 28360, "vin": [ { "gen": { "height": 28350 } } ], "vout": [ { "amount": 494385296643, "target": { "key": "fc9f7ec59a190179b9d864e2b6a448af068fe35641683fd0d9969a8a2cad79d2" } } ], "extra": [ 1, 85, 242, 146, 145, 66, 114, 72, 201, 231, 60, 200, 199, 206, 136, 73, 133, 149, 1, 113, 122, 139, 171, 27, 71, 131, 242, 63, 204, 98, 154, 83, 33, 2, 17, 0, 0, 0, 91, 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