Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c6647fda1368f19f9fea9e1b7eb0baed18cdba06e3c454702bbea0ec6af621e

Tx prefix hash: 4167b8bb13fdae9973bf2597cfe87a48672cb08478456a23c4921a5fcdb047ca
Tx public key: ddc8e8360183111fa3102f28f9d292727e59af3676bdd673a79be550f9c8f3eb
Timestamp: 1578310996 Timestamp [UCT]: 2020-01-06 11:43:16 Age [y:d:h:m:s]: 05:299:14:27:09
Block: 39664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1361959 RingCT/type: yes/0
Extra: 01ddc8e8360183111fa3102f28f9d292727e59af3676bdd673a79be550f9c8f3eb02110000000249b77a3d000000000000000000

1 output(s) for total of 453.500270892000 dcy

stealth address amount amount idx
00: 79276feef6ccd215a24e68b6f57b7c0d62d37b33277d4e6cd6e204aa8320e8af 453.500270892000 68777 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": 39674, "vin": [ { "gen": { "height": 39664 } } ], "vout": [ { "amount": 453500270892, "target": { "key": "79276feef6ccd215a24e68b6f57b7c0d62d37b33277d4e6cd6e204aa8320e8af" } } ], "extra": [ 1, 221, 200, 232, 54, 1, 131, 17, 31, 163, 16, 47, 40, 249, 210, 146, 114, 126, 89, 175, 54, 118, 189, 214, 115, 167, 155, 229, 80, 249, 200, 243, 235, 2, 17, 0, 0, 0, 2, 73, 183, 122, 61, 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