Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3762f9f1352b543fe4362fe85e210e397c6684f7231273ff0aab5a5624e5aacb

Tx prefix hash: 64c4a8d3f2249f1d8cc44f67428e9f1ea811d02ba56ba0152486eb84a964d5d4
Tx public key: 0e4871a711cd3638caa72239cc3258226f98a4d4d6d6363586e8af6d54ed3cf3
Timestamp: 1720643265 Timestamp [UCT]: 2024-07-10 20:27:45 Age [y:d:h:m:s]: 00:281:08:37:38
Block: 1062893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201025 RingCT/type: yes/0
Extra: 010e4871a711cd3638caa72239cc3258226f98a4d4d6d6363586e8af6d54ed3cf3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a25e791ab86ab548057425a45d522d645fe8c6bf2d1cd1d7823c7bc186db339 0.600000000000 1533404 of 15

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": 1062903, "vin": [ { "gen": { "height": 1062893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a25e791ab86ab548057425a45d522d645fe8c6bf2d1cd1d7823c7bc186db339" } } ], "extra": [ 1, 14, 72, 113, 167, 17, 205, 54, 56, 202, 167, 34, 57, 204, 50, 88, 34, 111, 152, 164, 212, 214, 214, 54, 53, 134, 232, 175, 109, 84, 237, 60, 243, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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