Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7301cacb1ad05771bedb7cfdab68d96fb28889e7a45d1276a67f06f1815f545

Tx prefix hash: 0094aab8ffcae51a503c0021b76200d66ed444b483f9fbff430d97d6c6512348
Tx public key: fe96ba3c0069efedcc0562761cc4b6bdfc6fba89e9ac41f093ca5e1c6abb9d81
Timestamp: 1705248107 Timestamp [UCT]: 2024-01-14 16:01:47 Age [y:d:h:m:s]: 01:002:19:52:59
Block: 935243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263340 RingCT/type: yes/0
Extra: 01fe96ba3c0069efedcc0562761cc4b6bdfc6fba89e9ac41f093ca5e1c6abb9d8102110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6362242777965d9cb5d02f943a0a93b8c93897fbbee5fa02cb1b39e2f5cd4cd 0.600000000000 1393259 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": 935253, "vin": [ { "gen": { "height": 935243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6362242777965d9cb5d02f943a0a93b8c93897fbbee5fa02cb1b39e2f5cd4cd" } } ], "extra": [ 1, 254, 150, 186, 60, 0, 105, 239, 237, 204, 5, 98, 118, 28, 196, 182, 189, 252, 111, 186, 137, 233, 172, 65, 240, 147, 202, 94, 28, 106, 187, 157, 129, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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