Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7697c2cd0c2a68142ba7129115fe75e3f0234ae80c4eede715ee2317f025275a

Tx prefix hash: ce0a8415ea7537314a5ac504931965814e7b398110410de0eb30061a34f058b8
Tx public key: be12afc1588800213ef025e7ee4324bbe2a74faea5300f071542e5466e6ecd3e
Timestamp: 1735052117 Timestamp [UCT]: 2024-12-24 14:55:17 Age [y:d:h:m:s]: 00:099:12:40:39
Block: 1182236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70895 RingCT/type: yes/0
Extra: 01be12afc1588800213ef025e7ee4324bbe2a74faea5300f071542e5466e6ecd3e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c57891039ef7c7449d1cd8fd4710eab7a0e3f2a0c26ef2f41b0c8cf0d843a7a9 0.600000000000 1668669 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": 1182246, "vin": [ { "gen": { "height": 1182236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c57891039ef7c7449d1cd8fd4710eab7a0e3f2a0c26ef2f41b0c8cf0d843a7a9" } } ], "extra": [ 1, 190, 18, 175, 193, 88, 136, 0, 33, 62, 240, 37, 231, 238, 67, 36, 187, 226, 167, 79, 174, 165, 48, 15, 7, 21, 66, 229, 70, 110, 110, 205, 62, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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