Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351a15043115442ffbb9f0415f0da1421322d59ddd0e3a70347dbaced4769899

Tx prefix hash: 527d492be7601d40319e796d152028b71f0ef9e59ec1e699d584a32e557b67ce
Tx public key: b4a184433936b7e267a9d9a3e1fabfd7e1fc8120c49d662a8c39dccaf0d20bb7
Timestamp: 1716608009 Timestamp [UCT]: 2024-05-25 03:33:29 Age [y:d:h:m:s]: 01:168:18:07:52
Block: 1029441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379197 RingCT/type: yes/0
Extra: 01b4a184433936b7e267a9d9a3e1fabfd7e1fc8120c49d662a8c39dccaf0d20bb702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a20bf458394f6fdda5b8fdacbd29274b804390eb5e5f4572c8042ba5535bb74c 0.600000000000 1497532 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": 1029451, "vin": [ { "gen": { "height": 1029441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a20bf458394f6fdda5b8fdacbd29274b804390eb5e5f4572c8042ba5535bb74c" } } ], "extra": [ 1, 180, 161, 132, 67, 57, 54, 183, 226, 103, 169, 217, 163, 225, 250, 191, 215, 225, 252, 129, 32, 196, 157, 102, 42, 140, 57, 220, 202, 240, 210, 11, 183, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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