Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d53f933ca4b218c5929a73dc629ef3b3741a131b6c0c888f35c03a962e431131

Tx prefix hash: 5c46a6133fa5aeadb93387645a55f2ce8a8d10634b8cb78b20baf82597cd1a07
Tx public key: 1eb58d3fccdbbaa6346d6dd72215cf6afb8a8084d1fc95ddd12683c65d7a48a0
Timestamp: 1731800999 Timestamp [UCT]: 2024-11-16 23:49:59 Age [y:d:h:m:s]: 00:138:08:02:25
Block: 1155285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98700 RingCT/type: yes/0
Extra: 011eb58d3fccdbbaa6346d6dd72215cf6afb8a8084d1fc95ddd12683c65d7a48a0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c329f4f2a79685ee457eb3eb410ccf8ae6a665b3da5af00b3eb37ff80bbb78f1 0.600000000000 1640900 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": 1155295, "vin": [ { "gen": { "height": 1155285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c329f4f2a79685ee457eb3eb410ccf8ae6a665b3da5af00b3eb37ff80bbb78f1" } } ], "extra": [ 1, 30, 181, 141, 63, 204, 219, 186, 166, 52, 109, 109, 215, 34, 21, 207, 106, 251, 138, 128, 132, 209, 252, 149, 221, 209, 38, 131, 198, 93, 122, 72, 160, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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