Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4cf2cad5ebcea65aff6819f561e126bffc609159527e8eda3d6828fca72567a

Tx prefix hash: 3df057e66483e81cf083642fc1b23bad8e9f91e00607f626219e5d814122e3a5
Tx public key: 7e0decfbc0f82c94e9f2b4ee25a26d1ead058308d479fbd5a8c6cf99c888b644
Timestamp: 1716546983 Timestamp [UCT]: 2024-05-24 10:36:23 Age [y:d:h:m:s]: 00:327:07:38:57
Block: 1028941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233935 RingCT/type: yes/0
Extra: 017e0decfbc0f82c94e9f2b4ee25a26d1ead058308d479fbd5a8c6cf99c888b64402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e755e4926b32713a4e60c84dc57a83d33c1ac46631852814c8a6d7cc26d60219 0.600000000000 1496942 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": 1028951, "vin": [ { "gen": { "height": 1028941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e755e4926b32713a4e60c84dc57a83d33c1ac46631852814c8a6d7cc26d60219" } } ], "extra": [ 1, 126, 13, 236, 251, 192, 248, 44, 148, 233, 242, 180, 238, 37, 162, 109, 30, 173, 5, 131, 8, 212, 121, 251, 213, 168, 198, 207, 153, 200, 136, 182, 68, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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