Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67157b0dce40f9d487380b0cfb715362caa894787c3690fb169f43a922fab536

Tx prefix hash: 3f9f9e889c75b3cab47405f4cf2076ba1077cec7c92c2ac54d00505d4857d923
Tx public key: 6a2259f1942b0ec06c02182a769b895cd45a99b2a660dfdc22fcf28b7efbec38
Timestamp: 1699362985 Timestamp [UCT]: 2023-11-07 13:16:25 Age [y:d:h:m:s]: 01:091:18:37:02
Block: 886467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326749 RingCT/type: yes/0
Extra: 016a2259f1942b0ec06c02182a769b895cd45a99b2a660dfdc22fcf28b7efbec3802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.709196922000 dcy

stealth address amount amount idx
00: 4b79fe5aac1df98a097ddb6decd2284d1597715cb612160183bc98fb278475b5 0.709196922000 1342294 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": 886477, "vin": [ { "gen": { "height": 886467 } } ], "vout": [ { "amount": 709196922, "target": { "key": "4b79fe5aac1df98a097ddb6decd2284d1597715cb612160183bc98fb278475b5" } } ], "extra": [ 1, 106, 34, 89, 241, 148, 43, 14, 192, 108, 2, 24, 42, 118, 155, 137, 92, 212, 90, 153, 178, 166, 96, 223, 220, 34, 252, 242, 139, 126, 251, 236, 56, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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