Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 073325d387f22edf505f40abdf75ab685f9201e2cb73b2d1ab98ed78de360c82

Tx prefix hash: c664a0d20f0bee4ca9454ebf8621b57a58237748f7e42ae6f3d623801faf1529
Tx public key: 676f766bfae913bd3f4be5aa076178f1e8d4ed1940571d39e03fa8753722d85e
Timestamp: 1673392046 Timestamp [UCT]: 2023-01-10 23:07:26 Age [y:d:h:m:s]: 02:077:01:01:26
Block: 672010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 576729 RingCT/type: yes/0
Extra: 01676f766bfae913bd3f4be5aa076178f1e8d4ed1940571d39e03fa8753722d85e0211000000018b7b6602000000000000000000

1 output(s) for total of 3.642099948000 dcy

stealth address amount amount idx
00: 81bc90416afd482f4b5dfecaaaec179b3f13d841bdcb699bfa21973fc8e6bbb1 3.642099948000 1113521 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": 672020, "vin": [ { "gen": { "height": 672010 } } ], "vout": [ { "amount": 3642099948, "target": { "key": "81bc90416afd482f4b5dfecaaaec179b3f13d841bdcb699bfa21973fc8e6bbb1" } } ], "extra": [ 1, 103, 111, 118, 107, 250, 233, 19, 189, 63, 75, 229, 170, 7, 97, 120, 241, 232, 212, 237, 25, 64, 87, 29, 57, 224, 63, 168, 117, 55, 34, 216, 94, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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