Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b65ecd88bfea2db0c01c7626c0f5ec2ebef6ba7660ef417279e17f156f2eaf75

Tx prefix hash: 4b8f04f9eafe97a2c6dc3dd5c6a309627526b18c1f34c796fdbbbda06fbd8615
Tx public key: cacda5dceace8fe861cd6b8785782ca4132b3ab75a88f16b0b40efaf556e698d
Timestamp: 1744648182 Timestamp [UCT]: 2025-04-14 16:29:42 Age [y:d:h:m:s]: 00:284:20:33:03
Block: 1261396 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201225 RingCT/type: yes/0
Extra: 01cacda5dceace8fe861cd6b8785782ca4132b3ab75a88f16b0b40efaf556e698d0211000000086c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e18e0a23a42248c35fb09e12c21be3d850b1a14b29aad28e7cfa82f9205c44f 0.600000000000 1748565 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": 1261406, "vin": [ { "gen": { "height": 1261396 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e18e0a23a42248c35fb09e12c21be3d850b1a14b29aad28e7cfa82f9205c44f" } } ], "extra": [ 1, 202, 205, 165, 220, 234, 206, 143, 232, 97, 205, 107, 135, 133, 120, 44, 164, 19, 43, 58, 183, 90, 136, 241, 107, 11, 64, 239, 175, 85, 110, 105, 141, 2, 17, 0, 0, 0, 8, 108, 152, 170, 61, 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