Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cdefe75ab92b261391aeb8b4796a60fc43fdba4b580ce66302d83b0ddc7ec3b

Tx prefix hash: dc3e3b354424daf4ed1dd5c2ce9afdbb20c3d4362ef7baf4f6cf9e5221eac8b2
Tx public key: e198a97458889f7631d3a68f5c0140e0e5432f6944a794361150724a3b0c755e
Timestamp: 1702595847 Timestamp [UCT]: 2023-12-14 23:17:27 Age [y:d:h:m:s]: 01:102:01:14:24
Block: 913261 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334056 RingCT/type: yes/0
Extra: 01e198a97458889f7631d3a68f5c0140e0e5432f6944a794361150724a3b0c755e02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd3214e42bbc4fe4a47e9cd5e9d48fa09a4733e775c46e9bab09f4b17a7e9975 0.600000000000 1370527 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": 913271, "vin": [ { "gen": { "height": 913261 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd3214e42bbc4fe4a47e9cd5e9d48fa09a4733e775c46e9bab09f4b17a7e9975" } } ], "extra": [ 1, 225, 152, 169, 116, 88, 136, 159, 118, 49, 211, 166, 143, 92, 1, 64, 224, 229, 67, 47, 105, 68, 167, 148, 54, 17, 80, 114, 74, 59, 12, 117, 94, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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