Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1018359225a30948c8e0bd9d8801a3e122dd32f1b3b9e74076cb3db69cc31ac

Tx prefix hash: f6f337f49c4be70690b8063412e1d33209623a8c278b4ebd0cc3377c2e8fb4ce
Tx public key: f900421cccca6cdbca7615ea31b7c250b62a236e3ccebc9391ba8bd0e62a32f5
Timestamp: 1733869665 Timestamp [UCT]: 2024-12-10 22:27:45 Age [y:d:h:m:s]: 00:101:13:32:15
Block: 1172446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72370 RingCT/type: yes/0
Extra: 01f900421cccca6cdbca7615ea31b7c250b62a236e3ccebc9391ba8bd0e62a32f5021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 532fdee4fe2415a8dfb05a38362cf02bcbd031087907f4cb2c8931037d4d4d2d 0.600000000000 1658337 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": 1172456, "vin": [ { "gen": { "height": 1172446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "532fdee4fe2415a8dfb05a38362cf02bcbd031087907f4cb2c8931037d4d4d2d" } } ], "extra": [ 1, 249, 0, 66, 28, 204, 202, 108, 219, 202, 118, 21, 234, 49, 183, 194, 80, 182, 42, 35, 110, 60, 206, 188, 147, 145, 186, 139, 208, 230, 42, 50, 245, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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