Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0971817f9bd9e6cf6d4aacab0c81675827a38b6e92e0055068028be7d9bdf8c3

Tx prefix hash: 02999258f01971c1b1e1e665c625f79c69dffd9aa74ad354d56981f698f8a08b
Tx public key: 579f04c0587b4dd3affc3bd9f0ed052da932136ba91f32d323755cfcdf013b47
Timestamp: 1716127429 Timestamp [UCT]: 2024-05-19 14:03:49 Age [y:d:h:m:s]: 00:236:06:51:10
Block: 1025448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169118 RingCT/type: yes/0
Extra: 01579f04c0587b4dd3affc3bd9f0ed052da932136ba91f32d323755cfcdf013b4702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41dc7b409892302a1fe2a1303666e2895cd9dbf1382bf9665eb12c7f077d0f1c 0.600000000000 1491963 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": 1025458, "vin": [ { "gen": { "height": 1025448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41dc7b409892302a1fe2a1303666e2895cd9dbf1382bf9665eb12c7f077d0f1c" } } ], "extra": [ 1, 87, 159, 4, 192, 88, 123, 77, 211, 175, 252, 59, 217, 240, 237, 5, 45, 169, 50, 19, 107, 169, 31, 50, 211, 35, 117, 92, 252, 223, 1, 59, 71, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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